Codecov Report

Merging #482 (ffddfe4) into master (834901e) will increase coverage by 0.07%.
The diff coverage is 82.79%.

@@            Coverage Diff             @@
##           master     #482      +/-   ##
==========================================
+ Coverage   92.92%   93.00%   +0.07%     
==========================================
  Files          15       15              
  Lines         791      800       +9     
==========================================
+ Hits          735      744       +9     
  Misses         56       56              

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 834901e...ffddfe4. Read the comment docs.

I think we want to follow BlueStyle?

By default, JuliaFormatter uses its own style, not BlueStyle. Can you check in a .JuliaFormatter.toml containing just style = "blue" and then re-run JuliaFormatter?

Also, now would be a good time to add the BlueStyle badge to the ReadMe.

I think we want to follow BlueStyle?

By default, JuliaFormatter uses its own style, not BlueStyle. Can you check in a .JuliaFormatter.toml containing just style = "blue" and then re-run JuliaFormatter?

Sure. In the end, I think it's more important to have an automatic formatter than what the style is, exactly.:)

Also, now would be a good time to add the BlueStyle badge to the ReadMe.

There's one already:

personally, i am against having a formatter CI job, because in my experience it is more pain than it is worth (and i say that as both the biggest contributor to BlueStyle and the person who worked with Dom to have it added to JuliaFormatter.jl). But i am not one of the bigger contributors here so am happy enough to be out voted

Personally, in my experience the pain from dealing with the autoformatter is much smaller than all the pain from arguments about style that are completely removed by having the autoformatter. But of course also happy for the core maintainers to vote as they see fit!

I am neutral about running the formatter as a one-off over the existing code (it makes style a bit more consistent

We can simply remove the formatter workflow from this PR again and just keep the formatting changes if you want to do that:)

but interferes with git blame),

A bit, but it's easy enough to "blame previous to this commit" (in the GitHub UI even easier than on the commandline):)

but if we are to do that we should use BlueStyle only

I've now removed all the changes from the previous format run, so its current state is BlueStyle changes only.

@oxinabox @sethaxen it's now properly following BlueStyle. do you want to accept it as is now, or just the format changes minus github action workflow, or is there anything else you'd like to change about it ?

OK, this worked out better than I initially expected seeing the PR.
Good.

I think we can merge this once the outstanding comments are solved.
Of which there are not so many and they are not too bad.

Excellent. Very nice work

Looks like the reviewdog doesn't actually make the suggestion for how to fix a line (so you could simply accept the review suggestion, instead of having to fix it manually). Not sure why that is - github actions permissions lacking ?

thanks